This repository was archived by the owner on Apr 21, 2026. It is now read-only.
Add unit tests for custom charm functionality#121
Closed
tonyandrewmeyer wants to merge 1 commit intocanonical:mainfrom
Closed
Add unit tests for custom charm functionality#121tonyandrewmeyer wants to merge 1 commit intocanonical:mainfrom
tonyandrewmeyer wants to merge 1 commit intocanonical:mainfrom
Conversation
Use ops.testing (Scenario) with the proposed charmcraft extension autoloading from canonical/operator#2367 to test the charm's custom code on top of the paas-charm base.
tonyandrewmeyer
requested review from
cbartz,
javierdelapuente,
yanksyoon and
yhaliaw
as code owners
Collaborator
|
@tonyandrewmeyer thank you for your contribution. we are no longer actively developing here (sorry this is brand hot news). I will close the PR. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
Use ops.testing (Scenario) with the new charmcraft extension autoloading from canonical/operator#2367 to test the charm's custom code on top of the paas-charm base.
Rationale
State transition tests are an inexpensive and quick way to validate charm functionality. Although the core functionality provided by the paas-charm base is tested in the base module, functionality that the charm adds on top of that should be tested by local to the charm tests.
Juju Events Changes
None.
Module Changes
None.
Library Changes
None.
Checklist
The documentation for charmhub is updated(N/A)urgent,trivial,complex)CHANGELOG.mdis updated with user-relevant changes.I don't believe I can add labels.